Computing device and method for the temporal arrangement of data

ABSTRACT

A device and method for management of an account. An event placement timeline is displayed. Account events are shown along the timeline. A preferred event time range or “safe zone” is shown along the timeline. The “safe zone” is the portion of the month during which it is safe to schedule certain events, like bill payments, with lower risk of NSF, overdraft or the like. The user moves a movable object into the “safe zone” to reschedule the account event in the “safe zone”, and the settings of the account are modified to automatically execute the account event at that time.

TECHNICAL FIELD OF THE INVENTION

This invention relates to the field of computer-implemented datamanagement.

BACKGROUND OF THE INVENTION

Computer systems, and associated methods, for data management are inwide use. Such systems and methods vary widely in configuration. Inaddition, there are many different types of data management to whichsuch systems and methods are applied.

One common example of data is financial data. There is a need forcomputer-implemented devices and methods that help account holders withcash flow management.

SUMMARY OF THE INVENTION

This patent application discloses a computing device and method fortemporal arrangement of data. In one embodiment the data is financialdata, and a computing device and method for managing an account aredisclosed.

In accordance with a first aspect of the invention, the computerreceives data of at least one account event associated with an account.An account event timeline image for showing the timing of the at leastone account account event is displayed on a display. An event placementtimeline image for scheduling of account events is also displayed on thedisplay. At least one account event image, each corresponding to anaccount event, is positioned along the account event timeline image.

One of the account events is identified for scheduling. The computerdetermines a proposed timing at which the identified account event is tobe scheduled (i.e. at which the identified account event will takeplace), and displays a proposed timing image visually associated withthe point on the event placement timeline corresponding to the proposedtiming. A movable object is also displayed.

When input is received in relation to the movable object (for example,it is dragged and dropped to the position on the event placementtimeline image corresponding to the proposed timing), the identifiedaccount event is scheduled for automatic execution at the proposedtiming.

In accordance with another aspect of the invention, the computerreceives data of at least one event associated with an account. An eventplacement timeline image, representing a future time period, isdisplayed on a display. Also displayed is at least one event image, eachcorresponding to a future event, positioned along the event placementtimeline image for showing the timing of each future event.

The computer determines a preferred event time range during which thelikelihood of a predefined adverse outcome resulting from one of thefuture events is reduced. A predefined adverse outcome might be, forexample, an insufficient funds event or an overdraft event.

The computer displays on the display a preferred event time rangeindicator—such as, for example, a highlighted region—along the timelineimage. The size of the indicator corresponds to the size of thepreferred event time range. The computer identifies one of the futureevents for movement into the preferred event time range to reduce thelikelihood of a predefined adverse outcome.

The computer displays a movable object. When input is received inrelation to the movable object—for example, by the object being draggedand dropped at a point on the timeline within the preferred event timerange—settings are modified to automatically execute the identifiedfuture event at a time within the preferred event time range.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example only, to figures whichillustrate embodiments of the invention, and in which:

FIG. 1 is a schematic diagram of the computing device;

FIG. 2 is an illustrative user interface screen showing events along twotimelines and a movable timing change object;

FIG. 3 is an illustrative user interface screen showing events along twotimelines and the movable timing change object being moved;

FIG. 4 is an illustrative user interface screen showing events along twotimelines and the completed movement of the timing change;

FIG. 5 is an illustrative user interface screen showing events along atimeline having a preferred event time range image, and a movable timingchange object;

FIG. 6 is an illustrative user interface screen showing events along atimeline having a preferred event time range image, and the movabletiming change object being moved;

FIG. 7 is an illustrative user interface screen showing events along atimeline having a preferred event time range image, and a completedmovement of the movable timing change object; and

FIG. 8 is an illustrative user interface screen, showing events along atimeline having a preferred event time range image, with the size of thepreferred event time range having been adjusted.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

One type of computer-implemented data management system is a financialmanagement computer system that can be used by customers of banks toaccess and manage bank accounts, or other similar accounts. In a typicalscenario, the customer has an account at a bank, and the bank provides acomputer-implemented system for facilitating the customer's managementof his account. That system permits connection by the customer through anetwork, usually the internet. The customer may be able to access thesystem via a personal computer, or a mobile device.

Typically, through the system, the customer can pay bills, or arrangeother debits from his account. Bill payments may be done in a one-offfashion. Alternatively, the debit or bill payment may be set to happenautomatically and periodically (e.g. on the same day of every month).

Another aspect of such systems is that they display to the user thetransactions (whether debits or credits) that have taken place on theaccount. Credits may include, for example, direct deposit to the accountof items such as payroll deposit, tax refunds, a P2P payment or anyother credit. The transactions shown would also typically includepayments made into the account that were initiated manually by thecustomer (e.g. going to the bank branch or ATM to deposit a cheque).

Debits to these account repositories typically include bills, whetherpaid manually at a bank branch, manually by online debit, orpre-authorized automatic monthly debit. Debits may also include eventsother than bill payments, such as automatic pre-authorized withdrawalsdeposited into a separate retirement savings account.

One concern of many account holders is cash flow. Even a customer whotakes in enough money each month to cover his expenses may experiencecash flow problems in his account if the debits and credits are nottimed appropriately. An example would be a salaried worker who earnssixty thousand dollars per year after income tax and other deductions.His pay is delivered semi-monthly, on the first and fifteenth of eachmonth, with each pay transaction consisting of a $2500 credit to hisaccount.

With monthly expenses from the account of about $5000, and a monthlyincome to the account of $5000, the customer should be able to cover hisexpenses. However, if more than half of his expenses come out of theaccount between his first pay on the first of the month and his secondpay on the fifteenth, there would be insufficient funds for at leastsome of his expenses. Such a state of affairs produces negativeconsequences not only for the customer, who fails to pay his bills ontime; but for the bank, which is saddled with greater administrativecost and effort.

Of course, the example cited above is simple as compared with manyreal-world examples. Typically, salaries are paid weekly or bi-weekly,while bills are due monthly. Furthermore, the timing of some kinds ofdebits, like car lease payments or mortgage payments, are pre-determinedat the time of funding which may not maintain their relevancy over anextended period of time.

In particular, the need exists for effective computer systems andcomputer methods that help customers improve cash flow and avoidnegative balance situations.

Referring now to FIG. 1, the computing device 10 includes a computer 12.The computer 12 may comprise any processor driven computer, including,for example, a desktop personal computer, a laptop computer, a mainframecomputer, a minicomputer, or a tablet. In one embodiment of computer 12includes processor 14, an accounting database 16 and a memory 18. Itwill be appreciated that the configuration of computer 12 may be anysuitable configuration. So, for example, the processor 14, accountdatabase 16 and memory 18 may or may not be co-located. Each of thesecomponents may itself comprise a single physical unit, or multiplephysical units operatively connected to one another as required. Some ofthese components may also be combined as appropriate. For example,account database 16 may be contained within memory 18.

In one embodiment, computer 12 is operatively connected to network 20.In a typical scenario, described below, network 20 comprises theInternet. However, it will be appreciated that other types of networksare comprehended by the invention. What is important is that the network20 functions to operatively connect computer 12, including processor 14,with a user display as described below. It will further be appreciatedthat a user display may be directly connected to computer 12, withoutuse of a network 20, and still be comprehended by the invention.

In one example network 20 is operatively connected to user computer 22,which includes display 21 and user input device 23. In some embodiments,user computer 22 may be a desktop computer, laptop computer, tablet orother computing and/or mobile device. Typically, the user computer 22may include an Internet browser to facilitate online communicationbetween a user and the computer 12. Input device 23 may be a mouse orsimilar device.

Processor 14 is operatively connected to memory 18, which memory 18stores computer readable instructions. Processor 14 is capable ofexecuting the computer readable instructions to cause the computingdevice to execute the actions and methods described herein. As describedfurther below, the actions and method steps include the determination ofproposing timing for account events, which in one embodiment are carriedout using recommendation engine 19.

In one embodiment, the account database 16 stores information aboutaccounts. In a typical scenario, the computing device of the presentinvention can be used by bank account holders to manage their bankaccounts, as discussed further below. It will be appreciated, however,that the invention comprehends other types of accounts, and not justbank accounts. Similarly, although the invention is being described indetail with respect to account events such as bill payments and paycheques, the invention comprehends any and all account events.

Thus, the account database 16 stores data relating to the accounts,including, inter alia, the account event data associated with eachaccount. This would typically include both the time of the events, thenature of the event (e.g. bill payment, automatic withdrawal, automaticdeposit), and the amount (i.e. how much the account balance changed as aresult of the event). Thus, the account database would store, forexample, data as to past credit events (events that increase thebalance, such as deposits of pay cheques), and debit events (events thatdecrease the balance, such as bill payments). In one embodiment thedatabase 16 also stores data on insufficient funds events, namely, whenan attempted debit cannot be completed because of an insufficientbalance, and overdraft events, namely, when a debit exceeds the balanceand the account goes into overdraft, but the debit is completed becausethe account has overdraft protection and is permitted to have a negativebalance.

In one embodiment, the account database 16 also stores account settings,including records of account events, such as bill payments, that arescheduled to be executed automatically. For example, a user may haveparticular bills, such as an internet service bill or fitness-club bill,due monthly, and may have configured his account to automate the paymentof this bill at the same time each month. In this example, the accountdatabase stores all of the information, such as the amount and day ofthe month for the bill payment.

The processor 14 can thus receive from database 16 data relating to theaccount, including past events and automatic payments, and use such datato assist the user in managing his account, as described below.

Referring now to FIG. 2, a user interface 24, being displayed byprocessor 14 on display 21, is shown. Within the user interface 24,based on the data received from database 16, the processor 14 displaysan account event timeline image 26 for showing the timing of at leastone of the account events reflected in the data received from thedatabase. In one embodiment, the account event timeline image 26represents a month, for example, a calendar month. Thus, account eventtimeline image 26 is marked at its top end, representing the beginningof the month, with the phrase “First of Month.” It is marked at itsbottom end, representing the end of the month, with the phrase “Last ofMonth.”

The account event timeline image 26 shown in FIG. 2 is a pictorialtimeline image, that is, it is a picture that takes the shape of a line.Thus, it is generally linear in configuration, and includes daymarkings, in the form of line segments 28, arranged substantiallylinearly. The account event timeline image, together with the accountimages along it, are a temporal arrangement of the account data. It willbe appreciated that such a form provides the user with an effectivevisual impression of the position of objects along the timeline, as willbe discussed further below.

Optionally, the account event timeline image 26 may also include aplurality of numbers along the timeline, arranged substantiallylinearly, each indicating a day of the month. For example, each day ofthe month may be marked by a number (e.g. 1-30 or 1-31). Alternatively,only some days of the month may be marked by numbers, while theremainder are not (e.g. only the 5^(th), 10^(th), 15^(th), 20^(th) and25^(th) of the month are marked by numbers).

Also, based on the data received from database 16, the processor 14displays along the account event timeline image 26 account event images,each representing an account event. Each account event image ispositioned along the account event image to show the timing of eachaccount event. In the embodiment shown in FIG. 2, the account events aredivided into debit events (displayed on one side of the image 26) andcredit events (displayed on the opposite side). The example debit eventimages include a phone bill modal 29, shown at the 3^(rd) of the month,mortgage bill modal 38, shown at the 8^(th) of the month, cable billmodal 30, shown at the 16^(th) of the month, and water bill modal 32,shown at the 27^(th) of the month. Example credit event images includetwo paycheque modals 34, shown as occurring at the 7^(th) and 21^(st) ofthe month.

The processor 14 is also causing to be displayed, based on the datareceived from database 16, an event placement timeline image 36, whichin FIG. 3 is labelled “Automation Adjuster.” In one embodiment, timelineimage 36 is used, as discussed below, for scheduling account events,such as an automated bill payment or other automated debit event.

In one embodiment the event placement timeline image 36 has the sameshape, day marking and numbering configuration as described above withrespect to the account event timeline image 26. In addition, thetimeline images 26 and 36 may be displayed in the side-by-sideconfiguration shown in FIG. 2. This allows a user to easily compareaccount events associated with the account, and their timing each month,with future events (which may in different embodiments be scheduled orunscheduled) associated with the account, and their timing within eachmonth. It also allows the user to easily and effectively execute andvisualize the process of scheduling an account event, as describedbelow. FIG. 2 shows a side-by-side configuration with the timelineimages oriented vertically, but a side-by-side configuration is possiblewith a different orientation.

In one embodiment, the processor 14, based on the data received from thedatabase 16, displays one or more future event images along the eventplacement timeline image 36, where each future event image correspondsto a future event. In FIG. 2, the example future debit event images area phone bill modal 29, a mortgage bill modal 38, and a water bill modal32.

In one embodiment, based on the received data, at least one scheduledevent image, each corresponding to a scheduled account event, isdisplayed along the timeline image 36. In this example, one scheduleddebit event (mortgage bill) is a automated bill payment scheduled at thesame time each month. Thus, its timing is stored in database 16. Thus,the data received from database 16 permits processor 14 to display thedebit event images 38 at the correct point along the event placementtimeline image 36. As with the timeline image 26, in one embodimenttimeline image 36 together with the events shown along it are a temporalarrangement of at least some of the account data, and proposed changedto that data as described below.

Furthermore, in one embodiment, the processor 14 is able to displayevents along timeline image 36 even when they are not automatic (e.g.phone bill and water bill in FIG. 2). The data from database 16 allowsprocessor 14 and recommendation engine 19 to predict from past eventswhen future events will occur.

The event images shown in FIG. 2 along timeline 36 also include twopaycheque modals 34 shown as occurring at the 7^(th) and 21^(st) of themonth. In this example, the data received from the database 16 includespast biweekly paycheque deposits that permit the processor 14 to displaypredicted future biweekly paycheque deposits, represented by modals 34.

The processor 14, for example, using recommendation engine 19,identifies one of the account events for scheduling, and determines aproposed timing at which the account event is to be scheduled (i.e atwhich the account event is to take place). In the example shown in FIG.2, the identified event is the cable bill payment, which is alsorepresented by modal 30 positioned on the account event image 26. Thus,the proposed timing can relate to an event that has occurred in theaccount in the past, but for which there is proposed a new timing toschedule the event, as in this example. Or, the proposed timing canrelate to an event that has never occurred in the account, but for whicha timing is proposed for scheduling.

In one embodiment, the processor 14 determines the proposed timing toavoid an insufficient funds event in the account. Thus, in the presentexample, the proposed timing for the cable bill payment is suggestedbecause the processor 14 determines that moving the cable bill paymentto a time after the second paycheque by scheduling it to beautomatically executed at that time will reduce the risk of aninsufficient funds event. In an insufficient funds event, there areinsufficient funds to pay the bill, and the bill payment is notcompleted successfully.

It will be appreciated that there are other possible grounds fordetermining the proposed timing. These could include, for example,avoidance of an overdraft event, which could occur when there isoverdraft protection associated with the account. Thus, the bill paymentwould successfully occur, but the account would be left in a negativebalance situation. The proposed timing might also be based on avoidance,or reduction, of account fees. For example, some bank accounts incurfees if the balance falls below a certain threshold. Thus, the processor14 can propose timing in order to change the cash flow profile of theaccount, so that the account balance does not fall below the threshold.Other grounds for determining proposed future timing may also be used.

In the example shown in FIGS. 2-4, the proposed timing for the cablebill payment is the 23^(rd) of the month, as shown in FIG. 4.Specifically, it is proposed that the cable bill payment be scheduled tobe automatically executed on the 23^(rd) of the each month. This timingwould be a change from the past timing of the cable bill, which was the16^(th) of the month. In addition, the cable bill payment would bescheduled for auto payment. In this example, the proposed timing is asingle day of the month. It will be appreciated, however, that theinvention comprehends that the proposed timing will be a range of morethan one day. Alternatively, the invention comprehends the proposedtiming being two or more non-contiguous days or day ranges.

Having determined the proposed timing, the processor 14 displays acorresponding proposed timing image 44 which is visually associated witha point on the event placement timeline image corresponding to theproposed timing. Processor 14 also displays a movable timing changeobject. In one embodiment, the timing change object is selectable, andthe user is prompted to select it. When input is received from the userin relation to the movable time change object, the processor modifiesaccount settings to schedule the identified account event (in thisexample, the cable bill payment) for automatic execution at the proposedtiming.

In the example shown in FIGS. 2-4, the proposed timing is the 23^(rd) ofthe month. The movable timing change object in this example is the modal30, which is positioned adjacent to the account event image. Thus, inthe present example, the modal 30 functions both as an account eventimage and as the movable timing change object, so that displaying modal30 constitutes displaying both an account event image and the movabletiming change object. However, it will be appreciated that the inventioncomprehends a movable timing change object separate from the past eventimages.

In the example shown in FIG. 2, the proposed timing image 44 is visuallyassociated with a point on the event placement timeline image 36corresponding to the proposed timing, by means of it being positioned atthat point, and overlapping the event placement timeline image 36 atthat point. It will be appreciated, however, that other types of visualassociation are comprehended by the invention. For example, a line couldbe displayed from image 44 to the point on the event placement timelineimage 36. What is important is that the proposed timing object 44 bevisually associated with the point corresponding to the proposed timing,so that the user can easily and effectively ascertain the portion of themonth at which the bill payment is proposed to be scheduled.

In the embodiment of FIG. 2, modal 30 contains a message to the usersuggesting movement of the cable bill payment to a different day of themonth to avoid an insufficient funds event. Arrow 46 is displayed, whichextends from modal 30 to proposed timing image 44. The arrow 46encourages the user to move object 30 to where proposed timing image 44is located. This movement is shown in FIG. 3.

Processor 14 modifies settings to schedule the identified event—in thisexample, the cable bill—for automatic execution at the proposed timing.The modification occurs once input is received in relation to themovable timing change object 30. In one embodiment, that input comprisesthe user selecting the movable object by dragging movable object 30using a mouse or other similar input device, and dropping it at theproposed timing image, or otherwise at a position along the timelineimage 36 representing the proposed timing. FIG. 3 shows the movement ofobject 30 taking place. Once this input is received, the accountsettings are modified, for example, in database 16, so that theidentified account event (in this case cable bill 30) is henceforthautomatically paid at the proposed future timing (in this case, the23^(rd) of the month).

It will be appreciated that the device 10 can provide for modes of inputdifferent from that described above. For example, a user may be able tosimply click on the object 30 using a mouse. However, it will beappreciated that dragging and dropping the object 30 provides aparticularly effective visual representation to the user of the changein bill payment timing.

FIG. 4 shows the cable bill image 30 after it has been moved to theevent placement timeline image 36. In one embodiment, once the movementis completed, the processor 14 displays an event change notificationimage 48. The notification image 48 confirms to the user that the changein timing for the cable bill has been completed.

In another embodiment, a separate and distinct movable timing changeobject is not displayed. Rather, an account event image associated withthe identified account event has its position changed. In response to aninput to change the position of the account event image corresponding tothe identified account event (e.g. dragging and dropping the accountevent image, or clicking on it), the identified account event isscheduled for automatic execution at the proposed timing. In theembodiment of FIGS. 2-4, the relevant account event image is image 30.

Another aspect of the invention is illustrated by the embodiment shownin FIGS. 5-8. Referring now to FIG. 5, a second user interface 124 isshown. Within UI 124, based on the data received from database 16, theprocessor 14 displays an event placement timeline image 136. Like thepreviously-described timeline images, the event placement timeline image136 represents a time period, which is in one embodiment a month, forexample, a calendar month. Timeline image at 136 may be marked at itstop end, representing the beginning of the month, with the phrase “Firstof Month.” It may be marked at its bottom end, representing the end ofthe month, with the phrase “Last of Month.” The timeline image 136represents a future or upcoming time period.

The timeline image 136 in one embodiment is a pictorial timeline image,that is, it generally takes the shape of a line. Thus, it is generallylinear in shape, and includes day markings, in the form of line segments128, arranged substantially linearly. It will be appreciated that such aform provides the user with an effective visual impression of theposition of objects along the timeline.

Optionally, the timeline image 136 may also include numbering, such asthe numbering described above in relation to the timeline images in FIG.2.

Also based on the data received from database 16, the processor 14displays along the timeline image 136 one or more event images, eachevent image corresponding to a future event. Typically, the futureevents comprise one or more debit events and one or more credit events.Each event image is positioned along the timeline image 136 for showingthe timing of each future event along the timeline image 136. It will beappreciated that the processor 14 using recommendation engine 19,predicts the future events in the account based on data from past eventsstored in database 16. Thus, the data shows, for example, that theaccount holder received a paycheque deposit biweekly. It also shows thatcertain bills, such as the mortgage bill and gas bill, are automaticallywithdrawn at such times each month. Even bills that are not automatic,like the water bill, can have their future payments times predicted withreasonable confidence, in light of past data on the timing of theirpayment.

As with the timeline images described in FIG. 2, in the embodiment shownin FIG. 5, the debit events are shown on one side of the timeline image,and the credit events on the opposite side. In FIG. 5, the debit eventsare on the left, and the credit events are on the right.

In FIG. 5, the example future debit events include cable bill modal 130,water bill modal 132, mortgage bill modal 138, and gas bill modal 140.The example future credit events include two paycheque modals 134.

Using the data from database 16, the processor determines a preferredevent time range, during which the risk of a predefined adverse outcomeresulting from one of the future events is reduced. Thus, the preferredevent time range is essentially a “safe zone”, that is, a part of themonth during which it is relatively safe to schedule a particular event,such as a bill payment.

The processor 14 then displays a preferred event time range indicatoralong the timeline image 138, the size of the indicator corresponding tothe size of the preferred event time range. In the example of FIG. 5,the preferred event time range indicator comprises highlighted region150. In one embodiment, highlighted region 150 functions to communicateto the user a time period during the month when it would be safe, basedon the account data, to schedule a particular event.

In the example of FIG. 5, the processor 14 is suggesting that the cablebill payment be rescheduled, and uses highlighted region 150 to indicateto the user the time range into which the cable bill payment should bemoved. It will be appreciated that, in the example of FIG. 5, the debitevent which is being recommended for rescheduling is a bill that waspreviously paid out of the account. However, it will be appreciated thatthe invention is not limited to such a case. For example, the user mayrequest that the system suggest a timing for a debit event that hasnever occurred in the account, but will in future.

It will be appreciated that in one embodiment the highlighted region 150is sized, shaped and configured to be conspicuous. In the example ofFIG. 5, it extends substantially across the width of the user interface,and it is bright green in colour. It is also positioned along andoverlaid on timeline image 136, so that its height H indicates clearlyto the user the size of the preferred event time range, or “safe zone.”

In one embodiment of this aspect of the invention, the height H isproportional to the size of the “safe zone.” Thus, when the size of the“safe zone” changes, as discussed below, the size of the highlightedregion 150 will change proportionally. The highlighted region 150 thusprovides the user with a visual feel for the size of the “safe zone.”The user does not need to laboriously count the days on the timelineimage. Rather, the user has a sense of the size of the “safe zone”simply from looking at it. If it is very thin (H is small), the userunderstands that only a small period during the month when he can safelyschedule the debit event in question. If the region 150 is thick or high(i.e. H is larger), then the user understands that a larger part of themonth is safe for the debit event in question.

The invention comprehends that the processor 14 can suggest more thanone preferred event time range, and thus can display more than onepreferred event time range indicator, at the same time. For example,consider a case in which a certain monthly debit needs to be scheduled.Based on the received data, the processor 14 may determine that thedebit can safely be made in two or more separate time periods during themonth (for example, between the 5^(th) and 10^(th), and between the20^(th) and 25^(th)). These time periods would collectively comprise thepreferred event time range. The invention further comprehends displayingtwo or more separate corresponding highlighted regions 150 (or anothertype of time range indicator), which would collectively comprise thepreferred event time range indicator.

It will be appreciated that the invention comprehends other forms ofpreferred event time range indicator besides highlighted region 150.What is important is that the indicator be positioned along the timelineto indicate the preferred time range for rescheduling the relevantfuture event.

The processor 14, for example using recommendation engine 19, identifiesone of the future events for movement into the preferred event timerange to reduce the likelihood of a predefined adverse outcome. In theexample of FIG. 5, that future event is the cable bill. At the top ofthe UI 124, and in a modal positioned within highlighted region 150,there is displayed a message suggesting that the cable bill be movedinto the “safe zone” represented by the highlighted region 150.

It will be appreciated that there are various possible predefinedadverse outcomes. They could include any one of an insufficient fundsevent, an overdraft event, or an excess account fees event. Or, theadverse outcome could be two or three of these events simultaneously.Thus, for example, an adverse outcome could be predefined as an outcomethat is either an insufficient funds event or an overdraft event. Or, itcould be predefined as any outcome that is either an insufficient fundsevent, an overdraft event, or an excess account fees event. Otherpredefined adverse outcomes are also comprehended by the invention.

The processor 14 displays a movable object. When input is received inrelation to the movable object, settings associated with the account aremodified by processor 14 to automatically execute the identified futureevent at a time within the preferred event time range.

In the example of FIG. 5, the movable object is cable bill modal 130.Cable bill modal 130, in this example, functions as both the movableobject and one of the event images. However, the invention comprehends amovable object separate from the event images.

In one embodiment, the input consists of the object 130 being draggedand dropped into the highlighted region 150, for example using a mouseor similar device. FIG. 6 shows the modal 130 being dragged and droppedinto the highlighted region 150. However, other types of input arecomprehended by the invention including, for example, clicking on theobject.

FIG. 7 shows the object 130 displayed within highlighted region 150after being moved there. As shown in FIG. 7, once the object 30 isdragged and dropped into the highlighted region 150, a notificationimage 148 is displayed to confirm to the user that the timing of theidentified future event has been changed.

It will be appreciated that, once the identified future event has beenrescheduled into the safe zone, the cash flow profile of the accountwill likely change, with the result that the size of the safe zone, andthus of the highlighted region, would change. In one embodiment, inresponse to the identified future event being rescheduled, the processor14 adjusts the size of the preferred event time range and the preferredevent time range indicator 150.

This adjustment is shown in FIG. 8. In the example of FIG. 8, the movingof the cable bill is complete, and it is proposed to add a new billpayment, namely, a magazine bill for $7.50 per month, represented bymovable object 152. The size of the preferred event time rangeindicator, H, has been adjusted to a smaller size as a result of theaddition of the cable bill. The preferred event time range now consistsof a smaller number of days.

It will be appreciated that features from the two aspects of theinvention may be combined in appropriate circumstances. As an example,it may be beneficial to make use of the highlighted region 150 in thefirst aspect of the invention, particularly when the proposed futuretiming comprises a range of time longer than a day. Other features ofthe two aspects of the invention may be combined when possible anddesirable to do so.

Embodiments of both aspects of the invention effectively impartinformation to the user by means of the use of pictures. Account eventsare shown positioned along a timeline, which gives a user a faster,better, more intuitive feel for the account events and their timing thana text or number-based description would. In the first aspect of theinvention, the use of pictures, namely, two timelines, allows the userto have a better and more intuitive feel for how the situation willchange in the account once the event is rescheduled. Similarly, in thesecond aspect of the invention, the preferred event time range indicatorcommunicates visually the size of the “safe zone”, because its sizealong the timeline image corresponds to the size of the “safe zone.”

Furthermore, the moving of movable objects to reschedule account eventsmakes the present system and method more intuitive and visual for theuser than, for example, a system where event timing is changed by typingletters or numbers. In the present system, the user feels like he isactually seeing the change in event timing. In addition, it is believedthat embodiments of the present invention, and in particular the movableobjects, provide a high level of perceived affordance to the user—thatis, the user intuitively understands that dragging and dropping theobject is a meaningful and useful act.

While illustrative embodiments of the invention have been described indetail above, it will be appreciated that various changes andmodifications may be made to these embodiments that are comprehended bythe invention.

The invention claimed is:
 1. A computer-implemented method, comprising:obtaining, by at least one processor, account event data identifying oneor more account events; by the at least one processor, and based on theaccount event data, generating and presenting an event placementtimeline image and an event image within a digital interface, the eventimage being associated with one of the account events and being disposedat a first position along the event placement timeline image, the firstposition being indicative of a timing of an expected occurrence of theassociated account event during a future temporal interval; determining,by at least one processor, a preferred event time range for theassociated account event, the preferred event time range comprising aportion of the future temporal interval and being associated with acorresponding temporal duration; by the at least one processing,generating and presenting, an indicator of the preferred event timerange within the digital interface, the indicator being disposed at asecond position along the event placement timeline image that isvisually associated with the portion of the future temporal interval,and a dimension of the indicator reflecting the corresponding temporalduration; by the at least one processor, receiving input data indicativeof selection of the event image, and based on the input data, performingoperations that schedule the associated account event for automaticexecution at a time within the preferred event time range; andperforming, by the at least one processor, operations that adjust thecorresponding temporal duration of the preferred event time range basedon the scheduling of the associated account event and that modify thedimension of the indicator within the digital interface in accordancewith the adjusted temporal duration.
 2. The computer-implemented methodof claim 1, further comprising, based on the received input data,presenting, the event image at a third position along the eventplacement timeline image, the third position corresponding to the timewithin the preferred event time range.
 3. The computer-implementedmethod of claim 1, wherein: an occurrence of the associated accountevent during the portion of the future temporal interval reduces alikelihood of a predefined adverse outcome resulting from the associatedaccount even; and the predefined adverse outcome comprises at least oneof an insufficient funds event or an overdraft event.
 4. Thecomputer-implemented method of claim 1, further comprising performingoperations that superimpose the indicator over a portion of the eventplacement timeline image, the superimposition of the indicatorestablishing a highlighted region within the event placement timelineimage that corresponds to the preferred event time range.
 5. Thecomputer-implemented method of claim 1, wherein: the one or more accountevents comprise at least one of a debit event or a credit event; and themethod further comprises: generating and presenting a debit event imagewithin a first portion of the digital interface; and generating andpresenting a credit event image within a second portion of the digitalinterface, the event placement timeline image separating the first andsecond portions of the digital interface.
 6. The computer-implementedmethod of claim 1, wherein: the future temporal interval comprises amonth; the preferred event time range comprises a portion of the month;the event placement timeline image comprises a series of day-markingsarranged within the digital interface along a longitudinal axis of theevent placement timeline image; and the event placement timelineincludes a plurality of numbers arranged within the digital interfacealong a longitudinal axis of the event placement timeline image, each ofthe numbers indicating a day of the month.
 7. The method of claim 1,wherein: the input data comprises a user input provided to an inputdevice coupled to the at least one processor; and the user inputcomprises a selection of the event image at the first position along theaccount event timeline image and a movement of the account event imageto a third position along the event placement timeline image, the thirdposition being disposed within the preferred event time range.
 8. Thecomputer-implemented method of claim 1, further comprising: generatingand presenting a moveable object within the digital interface; receivingadditional input data indicative of selection of the moveable object;and based on the additional input data, performing operations thatschedule the associated account event for automatic execution at thetime within the preferred event time range.
 9. A computing device,comprising: a memory for storing computer readable instructions; adisplay; and a processor operatively connected to the memory and to thedisplay, the processor being configured to execute the computer readableinstructions to: obtain account event data identifying one or moreaccount events; based on the account event data, generate and present,on the display, an event placement timeline image and an event imagewithin a digital interface, the event image being associated with one ofthe account events and being disposed at a first position along theevent placement timeline image, the first position being indicative of atiming of an expected occurrence of the associated account event duringa future temporal interval; determine a preferred event time range forthe associated account event, the preferred event time range comprisinga portion of the future temporal interval and being associated with acorresponding temporal duration; generate and present, on the display,an indicator of the preferred event time range within the digitalinterface, the indicator being disposed at a second position along theevent placement timeline image that is visually associated with theportion of the future temporal interval, and a dimension of theindicator reflecting the corresponding temporal duration; receive inputdata indicative of selection of the event image, and based on the inputdata, perform operations that schedule the associated account event forautomatic execution at a time within the preferred event time range; andperform operations that adjust the corresponding temporal duration ofthe preferred event time range based on the scheduling of the associatedaccount event and that modify, via the display, the dimension of theindicator within the digital interface in accordance with the adjustedtemporal duration.
 10. The computing device of claim 9, wherein theprocessor is further configured to execute the computer readableinstructions to, based on the received input data, present, on thedisplay, the event image at a third position along the event placementtimeline image, the third position corresponding to the time within thepreferred event time range.
 11. The computing device of claim 9,wherein: an occurrence of the associated account event during theportion of the future temporal interval reduces a likelihood of apredefined adverse outcome resulting from the associated account event;and the predefined adverse outcome comprises at least one of aninsufficient funds event or an overdraft event.
 12. The computing deviceof claim 9, wherein the processor is further configured to execute thecomputer readable instructions to superimpose the indicator over aportion of the event placement timeline image, the superimposition ofthe indicator establishing a highlighted region within the eventplacement timeline image that corresponds to the preferred event timerange.
 13. The computing device of claim 9, wherein: the one or moreaccount events comprise at least one of a debit event or a credit event;and the processor is further configured to execute the computer readableinstructions to: generate and present, via the display, a debit eventimage within a first portion of the digital interface; and generate andpresent, via the display, a credit event image within a second portionof the digital interface, the event placement timeline image separatingthe first and second portions of the digital interface.
 14. Thecomputing device of claim 9, wherein the future temporal intervalcomprises a month, and wherein the preferred event time range comprisesa portion of the month.
 15. The computing device of claim 14, whereinthe event placement timeline image comprises a series of day-markingsarranged within the digital interface along a longitudinal axis of theevent placement timeline image.
 16. The computing device of claim 15,wherein the event placement timeline includes a plurality of numbersarranged within the digital interface along a longitudinal axis of theevent placement timeline image each of the numbers indicating a day ofthe month.
 17. The computing device of claim 9, wherein: the computingdevice further comprises an input device coupled to the processor; andthe processor is further configured to execute the computer readableinstructions to receive the input data from the input device, the inputdata characterizing a user input provided to the input device, and theuser input comprising a selection of the event image at the firstposition along the account event timeline image and a movement of theaccount event image to a third position along the event placementtimeline image, the third position being disposed within the preferredevent time range indicator.
 18. The computing device of claim 9, furthercomprising an input device coupled to the processor, wherein theprocessor is further configured to execute the computer readableinstructions to generate and present a moveable object within thedigital interface; receive, from the input unit, additional input dataindicative of selection of the moveable object; and based on the inputdata, performing operations that schedule the associated account eventfor automatic execution at the time within the preferred event timerange.
 19. A tangible, non-transitory computer-readable medium storinginstructions that, when executed by at least one processor, cause the atleast one processor to perform a method, comprising: obtaining accountevent data identifying one or more account events; based on the accountevent data, generating and presenting an event placement timeline imageand an event image within a digital interface, the event image beingassociated with one of the account events and being disposed at a firstposition along the event placement timeline image, the first positionbeing indicative of a timing of an expected occurrence of the associatedaccount event during a future temporal interval; determining a preferredevent time range for the associated account event, the preferred eventtime range comprising a portion of the future temporal interval andbeing associated with a corresponding temporal duration; generating andpresenting an indicator of the preferred event time range within thedigital interface, the indicator being disposed at a second positionalong the event placement timeline image that is visually associatedwith the portion of the future temporal interval, and a dimension of theindicator reflecting the corresponding temporal duration; receivinginput data indicative of selection of the event image, and based on theinput data, performing operations that schedule the associated accountevent for automatic execution at a time within the preferred event timerange; and performing, by the at least one processor, operations thatadjust the corresponding temporal duration of the preferred event timerange based on the scheduling of the associated account event and thatmodify the dimension of the indicator within the digital interface inaccordance with the adjusted temporal duration.
 20. The tangible,non-transitory computer-readable medium of claim 19, wherein the methodfurther comprises: generating and presenting a moveable object withinthe digital interface; receiving additional input data indicative ofselection of the moveable object; and based on the additional inputdata, performing operations that schedule the associated account eventfor automatic execution at the time within the preferred event timerange.